V402 — CHARACTER FILE IMPORT + PROTAGONIST CAMPAIGN AUTOSAVE
===========================================================
Base: V401 login persistence, account-filtered native Import, native Export,
V399 no-respawn character handling. All source files in this ZIP are read-only.

WHAT CHANGED
1. Character Creation > Import immediately opens Character File Import.
   The "Saved Game / Partie sauvegardee" choice is bypassed; the existing
   V401 account-filtered CHARGEN_IMPORT list and confirmation guard remain.
   BG2's other Load Game screens are not disabled.

2. The live protagonist is characters[1]. An account-tagged full-game save is
   requested once after 30 seconds of eligible in-game play and every five
   minutes thereafter, only while that protagonist has current HP > 0.
   This uses BG2's native saveScreen:SaveGame API and one reused
   DRK<account-length>_<account>_<campaign>_SOLO_AUTOSAVE slot for each host
   account/campaign (SoA, ToB, TBP). It is NOT a CHR export.
   * No auto saves while dead, during cutscenes, before game world loads,
     during Play transitions, or while another player/character fills slots
     2-6 (existing V318 'protagonist-only clean save' safeguard).
   * Guest clients cannot create these host checkpoints.
   * No files are copied, revived, moved or deleted by V402.
   * Saves contain all world/quest data. Native BG2 cannot save only one
     protagonist without also capturing the live party. V318's empty-guest
     restriction prevents silently saving other users' characters.

3. Resume Campaign opens the game's native LOAD system and selects the newest
   save matching the logged-in account and chosen campaign, automatically
   triggering its normal full-game LoadGame action. Saves belonging to other
   accounts/campaigns are never selected by this new path. If no qualifying
   save exists, the LOAD screen remains available for manual inspection.

IMPORTANT — WINDOWS IN-GAME TESTS REQUIRED
- BG2 version 2.7.3: confirm that calling saveScreen:SaveGame from the world
  UI actually persists an mpsave/ save-game slot; success of a Lua pcall by
  itself does NOT prove the engine wrote a save. If BG2 refuses the call, do
  not infer that Resume Campaign can load a checkpoint.
- Test SoA, ToB, TBP separately. Confirm the account name + campaign prefix.
- Start protagonist alive and alone, wait 30+ seconds, then test that one
  autosave appears in BG2's native saved games. After five minutes, verify
  that the same slot is updated rather than a duplicate folder appearing.
- Confirm no autosave while protagonist HP <= 0 or while guests occupy slots.
- Restart BG2 and use Resume Campaign: the most recent owned save should load.
- Verify Drakhysys and Kronas still see/import only their own 5+2 CHR files.
- Verify characters/ never gets automatically repopulated or moved.

Installation: exit BG2, run SETUP_IN_GAME_ACCOUNTS.bat and select your game
folder plus the actual engine.lua profile folder (for example Documents\\
BaldursGate2Online containing Baldur.lua). Existing saves, character files,
engine.lua, and original V401 ZIP are not changed by packaging this update.
